bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 11 Jan 2020 10:14:46 +0000 (10:14 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Sat, 11 Jan 2020 10:14:46 +0000 (10:14 +0000)
commit7d39e292fa2db39b5091e321ff70a22586219b27
tree29796a7692e1f495138a2d5fb30e69b390807626
parent84c73ca489b641506f55a422f3a921301e25abd2
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h